FastNo server uploadURL/Query

URL Encoder / Decoder & Parser - Percent Encoding

Handle URL encoding/decoding plus Query String, UTM and duplicate-parameter analysis Browser only in one place.

Related toolsBase64 Encoder & DecoderRegex Tester & ReplacerJSON/XML Formatter & Validator Cron Expression Tool Timestamp / Time Zone Converter My IP Address QR Code Generator

Convert

Cleanup options

0
Parameters
0
UTM
0
Duplicate keys
Waiting
Status
Processing limit: URL/text input up to 1 MB

Query Parameters

Parsed URL details will appear here.

Output

Output will appear here.

URL components

Parse the URL to view its components.

Encoding and Parsing URLs Correctly

URL encoding is contextual: encoding an entire URL as plain text is different from encoding a query value or path component. Parsing first helps preserve the scheme, host, path, query keys, and fragments while changing only the part that actually needs percent-encoding.

Encode values, not blindly the whole address

A complete URL contains structural characters such as : / ? & = and #. Encoding the whole string can turn those delimiters into data and make the address unusable. Encode user-provided parameter values or path segments with the function appropriate to that component.

Query order and empty values can matter

Sorting parameters is helpful for comparison, but some signed URLs, legacy backends, or cache keys depend on exact order. Likewise, removing empty values can change semantics when a server distinguishes key= from a missing key.

Decoding is for inspection, not automatic rewriting

Showing decoded values makes UTM tags and parameters easier to read, but a decoded character may need to stay percent-encoded in the final URL. Always test the reconstructed URL in the system that will consume it.

Before editing a URL

Helpful information